Harden validation and refresh project tooling#323
Merged
Conversation
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
THIS PROJECT IS IN MAINTENANCE MODE. We accept pull requests for bug fixes only. New features are not accepted.
Description
Refreshes maintenance tooling, dependency metadata, GitHub-facing documentation, and the MkDocs site. It also hardens Telegram init data validation around query parsing, expiry handling, typed result serialization, and third-party validation without changing public method names.
Related Issue
No linked issue. This is a maintenance update for dependency/tooling refresh, documentation accuracy, and validation correctness found during repository review.
Motivation and Context
The project needed a current Poetry 2.x setup, updated CI tooling, clearer public documentation, and stricter handling of valid Telegram payloads. The auth changes fix edge cases around encoded query values, zero-duration expiry checks, runtime dataclass types, malformed init data, and third-party validation ergonomics.
How Has This Been Tested (if appropriate)?
PYENV_VERSION=3.13.12 make flakePYENV_VERSION=3.13.12 make mypyPYENV_VERSION=3.13.12 make black-lintPYENV_VERSION=3.13.12 make testPYENV_VERSION=3.13.12 poetry run pytest --cov=telegram_webapp_auth --cov-branch --cov-report=html testsPYENV_VERSION=3.13.12 poetry run mkdocs build --strict./actionlint -colorgit diff --checkScreenshots (if appropriate):
Not applicable.